-
Notifications
You must be signed in to change notification settings - Fork 1.1k
First draft of firestore-basics skill #9719
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Summary of ChangesHello @joehan, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces the initial draft of a new 'firestore-basics' skill. Its primary goal is to serve as a comprehensive resource for users looking to understand and implement Cloud Firestore, covering essential aspects from initial setup and configuration to securing data with rules and integrating the SDK into applications. Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a new 'firestore-basics' skill, providing a foundational guide to Cloud Firestore. The skill is well-structured into provisioning, security rules, and SDK usage. My review includes suggestions to enhance the examples and documentation to make them more practical for users. Specifically, I've recommended improving how data is logged in the SDK examples, adding more advanced security rule patterns like data validation and separated read/write access, and including a section on deploying Firestore configurations. These suggestions align with the TODOs mentioned in the pull request description and aim to make the skill more complete.
|
/gemini review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a new 'firestore-basics' skill, providing comprehensive documentation and code examples for web, Android, and iOS. The content is well-structured and covers key aspects of Firestore, including provisioning, security rules, SDK usage, and indexes. My review focuses on improving the correctness and clarity of the code snippets and documentation. I've identified several issues, such as incorrect API usage in the Android SDK examples, unsafe coding practices like force-unwrapping in Swift, and formatting problems in the markdown files. I've provided specific suggestions to fix these issues, which will enhance the quality and reliability of the skill for developers.
|
@joehan Are the pricing, prompt, and guide changes related to the new skill(s) or are these separate changes? At first glance they seem out of place here. Unless they are just coming from syncing to main? Maybe just do that separately? |
|
|
||
| ## Manual Initialization | ||
|
|
||
| For non-interactive environments (like AI agents), it is recommended to manually create the necessary configuration files instead of using `firebase init`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems a bit ambiguous. Maybe something like:
| For non-interactive environments (like AI agents), it is recommended to manually create the necessary configuration files instead of using `firebase init`. | |
| Initialize the following firebase configuration files manually. Do not use `firebase init` because <reason>. |
(insert appropriate <reason>)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the reason btw? :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call. is 'becuase it expects interactive inputs, and those will confuse you Mr. AI agent'
Yep, those are just from syncing to main (and forgetting to sync launch.skills) - will get the launch branch up to date before merging |
Slightly more polished draft of the firestore-basics skill. It covers:
TODOs